• 8.0.5 - 2022-11-04
  

  This release fixes a few minor TS issues.

  What's Changed

  • Provider: pass state (S) generic through to ProviderProps by @ OliverJAsh in #1960
  • wrap equalityFn type in NoInfer by @ phryneas in #1965
  • Fix wrapped component prop types when passing nullish mapDispatchToProps by @ marconi1992 in #1928

  Full Changelog: v8.0.4...v8.0.5

• 8.0.4 - 2022-09-23
  

  This patch release fixes some minor TS types issues, and updates the rarely-used areStatesEqual option for connect to now pass through ownProps for additional use in determining which pieces of state to compare if desired.

  Note: 8.0.3 was accidentally published without one of these fixes. Use 8.0.4 instead.

  Changelog

  TS Fixes

  We've fixed an import of React that caused issues with the allowSyntheticDefaultImports TS compiler flag in user projects.

  connect already accepted a custom context instance as props.context, and had runtime checks in case users were passing through a real value with app data as props.context instead. However, the TS types did not handle that case, and this would fail to compile. If your own component expects props.context with actual data, connect's types now use that type instead.

  The ConnectedProps<T> type had a mismatch with React's built-in React.ComponentProps<Component> type, and that should now work correctly.

  Other Changes

  The areStatesEqual option to connect now receives ownProps as well, in case you need to make a more specific comparison with certain sections of state.

  The new signature is:

  {
    areStatesEqual?: (
      nextState: State,
      prevState: State,
      nextOwnProps: TOwnProps,
      prevOwnProps: TOwnProps
    ) => boolean
  }

  What's Changed

  • Don't require allowSyntheticDefaultImports: true by @ apepper in #1924
  • Fixed type issue with ComponentProps from older @ types/react by @ Andarist in #1956
  • connect: pass ownProps to areStatesEqual by @ jspurlin in #1951
  • Omit built-in context prop if user component props include context by @ markerikson in #1958

  Full Changelog: v8.0.2...v8.0.4

• 8.0.3 - 2022-09-23
  

  This release was accidentally published without an intended fix - please use v8.0.4 instead

• 8.0.2 - 2022-05-22
  

  This patch release tweaks the behavior of connect to print a one-time warning when the obsolete pure option is passed in, rather than throwing an error. This fixes crashes caused by libraries such as react-beautiful-dnd continuing to pass in that option (unnecessarily) to React-Redux v8.

  What's Changed

  • Show warning instead of throwing error that pure option has been removed by @ ApacheEx in #1922

  Full Changelog: v8.0.1...v8.0.2

• 32e40e4 Merge pull request #1928 from marconi1992/fix/1927
• ff7d96b fix: type when passing nullish mapDispathToProps
• 5082af7 Merge pull request #1965 from reduxjs/draft/amazing-rosalind
• bafe55e Add typetests
• fc3954a Update test matrix to Node 16 and TS 4.9
• 401250e also update TypedUseSelectorHook
• 3b06061 wrap type in
• ad40b97 Merge pull request #1960 from OliverJAsh/patch-1
• 8cf538c Merge pull request #1966 from ethen001/chores/custom-equality-fn-docs
• 54d8096 chore(docs): added custom equalityFn example
• 9e09869 `any` -> `unknown`
• e7017ed Add type test
• b50f392 `Provider`: pass state (`S`) generic through to `ProviderProps`
• 70a167e Release 8.0.4
• 3c9766e Merge pull request #1958 from reduxjs/bugfix/connect-context-prop
• 4fcd42c Release 8.0.3
• 69413ff Merge pull request #1951 from jspurlin/jspurlin/passOwnPropsToASE
• 1236861 Use a `Mapped` type to simplify the final displayed types for components
• f40d82d Omit built-in `context` prop if user component props include `context`
• bbc546e Fixed type issue with `ComponentProps` from older `@ types/react` (#1956)
• 527eb36 update type of actualChildProps to be more accurate
• 4122b1c Merge branch 'jspurlin/passOwnPropsToASE' of https://github.com/jspurlin/react-redux into jspurlin/passOwnPropsToASE
• 405d39b Update connect.md
• 0846e26 update connect docs

Compare